fix: define retry limit in retry config#693
Merged
gr2m merged 1 commit intosemantic-release:masterfrom Sep 9, 2023
Merged
Conversation
dhensby
force-pushed
the
pulls/rate-limit-retry
branch
from
1e3f1b4 to
59b679e
Compare
dhensby
changed the title
|
🎉 This PR is included in version 9.0.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Potential fix to #644
The current retry logic attempts to see if the retry limit has been hit but it does this by checking against an undefined value.
This may have been an oversight from #487 as
RETRY_CONFIGdid have aretriesproperty, but it was removed.